Blog

Curt Gratz

February 09, 2015

Spread the word


Share your thoughts

You may be wondering where all that amazing debugging information went in your ColdBox 4.0 application.  Have no fear.  You can still have your cake and eat it too.  We modularized it (sensing a theme in ColdBox 4.0 yet?) So, how do you get all that wonderful debugging info?

Easy! Using CommandBox, run the following command.

box install cbdebugger --saveDev

Notice the --saveDev we added to our command.  This is handy as it tells CommandBox that you only want this as a dependency for your application in development.  

Once the debugger module is installed, you can control the settings via the debugger structure in your main Coldbox config file.  

Also, if you need access to the debugger service or the timer, they are available via the following WireBox mappings.

  • debuggerService@cbdebugger
  • timer@cbdebugger

Just call getInstance() on either to snag them as needed.

Debug to your heart's content.

Add Your Comment

(2)

Feb 11, 2015 18:16:55 UTC

by Jim Priest

If you are like me and just getting started with ColdBox - once you have installed the debugger module, look under /modules/cbdebugger/readme.md and there is an example 'Debugger Settings' of what you need to copy to your ColdBox config file to enable things.

Feb 27, 2015 00:03:15 UTC

by Dan O'Keefe

I get "command cannot be resolved". Isn't it supposed to just be "install cbdebugger --saveDev"?

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025